Digital content translation techniques and systems

ABSTRACT

Digital content translation techniques and system are described. In one example, source digital content is linked via metadata to different derived format versions that are generated from the source digital content. The metadata, for instance, may be used to locate source digital content that generated a particular derived format version that is in use by a service provider system. The source digital content, once identified and located, may then be used to improve efficiency and accuracy in translation of text or images included as part of the source digital content. The updated source digital content is then used to generate a derived format version that includes the translated text or other portion, e.g., an image.

BACKGROUND

Digital content creators may employ a variety of different formats inorder to support output of digital content in a variety of differentscenarios, such as for use in a webpage, mobile application, part of apresentation, for printing on a physical medium (e.g., publishing onpaper), and so forth. To do so, digital content creators typicallycreate source digital content through interaction with a contentmanagement system. The source digital content is then translated into avariety of different derived format versions to support output in thesedifferent usage scenarios.

A digital content creator, for instance, may first create the sourcedigital content through interaction with a content management systemthat supports rich functionality usable to support display and furthermodification of the content, e.g., through use of layers as part of aPhotoshop® Document (PSD) format. The content management system is thenused to generate derived format versions to support output in differentusage scenarios, such as to use a portable document format (PDF) orjoint photographic experts group (JPEG) format for online use, a taggedimage file format (TIFF) for publishing, and so forth. In this way, thedifferent content format versions address storage and communicationconsiderations of these scenarios as part of content consumption. Thedigital content versions are then disseminated to service providersystems for use, such as part of a webpage, for use in publishing, andso forth.

In some instances, the source digital content is also configured formultilingual use. However, the variety of different derived formatversions may present a challenge for translation into differentlanguages. A creative professional, for instance, may generate a banneras source digital content for a retail website through interaction witha content creation service. This source digital content is then used togenerate derived format versions as previously described, which is thenprovided to a service provider system for dissemination to potentialcustomers.

In order to support use of a different language, the service providersystem may then wish to translate text included as part of the derivedformat version. However, in conventional techniques the service providersystem typically does not have access to the source digital content nora way or identifying the source digital content used to generate thederived format version. Consequently, the service provider system istypically forced to send the derived format version that is included aspart of the retail website for translation, e.g., a derived formatversion as a JPEG. The text from the JPEG is then translated andembedded as part of the JPEG, which may result in noticeable artifacts,a diminished viewing experience, and is cumbersome to perform.

SUMMARY

Digital content translation techniques and system are described. In oneexample, source digital content is linked via metadata to differentderived format versions that are generated from the source digitalcontent. The metadata, for instance, may be used to locate sourcedigital content that generated a particular derived format version thatis in use by a service provider system.

The source digital content, once identified and located, may then beused to improve efficiency and accuracy in translation of text or imagesincluded as part of the source digital content. In one example, this isachieved by locating a text layer included as part of the source digitalcontent to a translation service, which is then translated and providedback to update the source digital content, e.g., for support of a newlanguage.

The updated source digital content is then used to generate a derivedformat version that includes the translated text. In this way, a unifiedsystem is supported having increased richness, computational efficiency,and accuracy in use of translations by providing a “clear view” of thetext or image, supports copyright protection when limiting communicationto the text layer (or relevant image layer) and not other layers of thesource digital content, and so forth. Other examples are alsocontemplated as further described in the following sections, includingautomatic generation of derived format versions for dissemination (e.g.,to service provider systems) in response to an update of the sourcedigital content.

This Summary introduces a selection of concepts in a simplified formthat are further described below in the Detailed Description. As such,this Summary is not intended to identify essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. Entities represented in the figures may be indicative of one ormore entities and thus reference may be made interchangeably to singleor plural forms of the entities in the discussion.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ translation linkage and metadata techniquesdescribed herein.

FIG. 2 depicts a system in an example implementation showing generationand management of metadata to link source digital content with a derivedformat version derived from the source digital content.

FIG. 3 depicts a system in an example implementation in which atranslation is generated to update source digital content.

FIG. 4 is a flow diagram depicting a procedure in an exampleimplementation in which a derived format version is updated as includinga translated version of text through use of source digital content.

FIG. 5 depicts a system in an example implementation in which derivedformat versions are automatically generated based on an update to sourcedigital content.

FIG. 6 is a flow diagram depicting a procedure in an exampleimplementation in which several different derived format versions areupdated as including a translated portion through an update to sourcedigital content.

FIG. 7 illustrates an example system including various components of anexample device that can be implemented as any type of computing deviceas described and/or utilize with reference to FIGS. 1-6 to implementembodiments of the techniques described herein.

DETAILED DESCRIPTION

Overview

Digital content creators typically employ different formatted versionsof source digital content in order to target different deliverymechanisms for dissemination to users, which are referred to as “derivedformat versions” in the following. To do so, the source digital contentis created and edited in a rich format (e.g., PSD) through interactionwith a computing device and then converted to other formats to addressstorage and delivery considerations, such as a JPEG for a webpage, TIFFfor a printed publication, and so forth. This presents challengesregarding translation to service provider systems that receive aconventional derived format version of the source digital content butnot the source digital content itself.

In one example, a webpage may be configured for output in a variety ofdifferent languages. Translation of the derived format version tosupport output in a different language in conventional techniquesinvolves communication of the derived format version to a translationservice system, e.g., a JPEG. The text from the JPEG is then translatedand embedded as part of the JPEG, which may result in noticeableartifacts, a diminished viewing experience, and is cumbersome andcomputationally expensive to perform.

Accordingly, digital content translation techniques and system aredescribed. In one example, metadata is generated (e.g., extracted ifalready present) by a content management system that supports a linkbetween source digital content and derived format versions formed fromthe source digital content. The metadata, for instance, may beassociated with the derived format version (e.g., as part of, maintainedin a separate data repository, and so forth) that identifies the sourcedigital content that is used to generate this version. Therefore,translations of text or digital images included as part of the derivedformat version may leverage identification and availability of thesource digital content to increase accuracy in the translation, updatean appearance of a derived format version that includes the translation(e.g., automatically and without user intervention), as well as supportincreased efficiency in network and computational resources.

A service provider system, for instance, may disseminate a webpage inmultiple languages. To add a new language, metadata associated with thederived format version is used to locate source digital content, e.g.,at a content management system. Text or an image to be translated isthen extracted from the source digital content (e.g., a respectivelayer) and that text or image, without other portions of the sourcedigital content, is then communicated to a translation service system.As a result, network communication efficiency and protection ofpotentially copyrighted material is increased.

The translation service system then translates the text or image. Thismay include output in a user interface and receive of user inputs toperform the translation, use of machine learning translation techniquesthat do not involve user inputs, or a combination thereof. Thetranslation is then communicated back to the content management system,which is used to update the source digital content (e.g., to addadditional layers for each language). This may include creation of a newversion of the source digital content or appending the update as anadditional layer, which may be used to improve storage efficiency of acomputing device.

The updated source digital content is employed by the content managementsystem to generate derived format versions (e.g., a JPEG, TIFF, etc.), arelevant one of which is then communicated to the service providersystem. In this way, the translation has increased accuracy overconventional techniques that relied solely on the derived format versionthat is available. These techniques and systems also have increasedcomputational and network efficiency through communication andutilization of relevant portions of the source digital content and notother portions (e.g., layers). Further discussion of these and otherexamples is contained in the following sections and shown incorresponding figures.

In the following discussion, an example environment is first describedthat may employ the techniques described herein. Example procedures arethen described which may be performed in the example environment as wellas other environments. Consequently, performance of the exampleprocedures is not limited to the example environment and the exampleenvironment is not limited to performance of the example procedures.

Example Environment

FIG. 1 is an illustration of a digital medium environment 100 in anexample implementation that is operable to employ techniques describedherein. The illustrated environment 100 includes a content managementsystem 102, service provider system 104, and translation service system106 that are communicatively coupled, one to another, via a network 108.Computing devices that implement the content management system 102,service provider system 104, and translation service system 106 may beconfigured in a variety of ways.

A computing device, for instance, may be configured as a desktopcomputer, a laptop computer, a mobile device (e.g., assuming a handheldconfiguration such as a tablet or mobile phone as illustrated), and soforth. Thus, the computing device may range from full resource deviceswith substantial memory and processor resources (e.g., personalcomputers, game consoles) to a low-resource device with limited memoryand/or processing resources (e.g., mobile devices). Additionally, acomputing device may be representative of a plurality of differentdevices, such as multiple servers utilized by a business to performoperations “over the cloud” as described in FIG. 7.

In the illustrated example, the service provider system 104 isconfigured to disseminate a derived format version 110, which isillustrated as stored in a storage 112, e.g., memory or othercomputer-readable storage medium as described in greater detail inrelation to FIG. 7 that may be implemented local or remote to theservice provider system 104. The service provider system 104, forinstance, may be configured to output a webpage that includes thederived format version 110, e.g., text as part of a banner, home page,and so forth. In order to translate the derived format version 110, theservice provider system 104 leverages metadata 114 associated with thedigital content version 110. The metadata 114 may be configured in avariety of ways to provide a link between the derived format version 110and source digital content 116 used to generate that version. Themetadata 114, for instance, may include a source content identifier thatis usable to uniquely identify and locate the source digital content116, which is illustrated as stored in a content repository 118 (e.g.,storage device) of a content management system 102 accessible via anetwork 108.

The content management system 102 includes a digital content managermodule 120 that is implemented by at least one computing device tomanage creation, editing, and/or storage of digital content, an exampleof which is illustrated as the source digital content 116. Example offunctionality of the digital content manager module 120 include a linkmanager module 122 and a translation manager module 124. The linkmanager module 122 is configured to generate and manage use of metadata114 that provides a link between the source digital content 116 andderived format versions generated from the source. An example ofgeneration of the metadata 114 by the link manager module 122 isdescribed in greater detail in relation to FIG. 2.

Based on the linkage provided by the metadata 114, the link managermodule 122 is configured to locate the source digital content 116 fromthe content repository. A translation manager module 124 is then used toextract a portion 126 of the source digital content 116 that is to betranslated, e.g., text, an image, or other portion of digital content.In an implementation, the portion 126 and not other portions of thesource digital content 116 are then communicated by the translationmanager module 124 via the network 108 to a translation service system106. For example, the translation manager module 124 may extract a textlayer from the source digital content 116 as the portion 126 andcommunicate the text layer and not other layers of the source digitalcontent 116 via the network 108. As a result, computational and networkefficiency are increased as well as providing protection for the otherlayers that may be copyrighted.

The translation service system 106, upon receipt of the portion 126,employs a digital content translation module 128 that is configured togenerate a translation of the portion 126. Generation of the translationmay be performed in a variety of ways, such as through output in a userinterface, automatically and without user intervention through machinelearning or other computer translation techniques, and so forth.Regardless of how generated, the translated portion 130 is thencommunicated back to the content management system 102. Although thetranslation service system 106 and the content management system 102 areillustrated separately in this example, this functionality may becombined into a single entity (e.g., a single system), further dividedacross additional entities, and so forth.

The digital content manager module 120, upon receipt of the translatedportion 130 by the translation manager module 124, updates the sourcedigital content 116 with the translated portion 130, e.g., changes alayer or appends another layer to the source digital content 116. Theupdated source digital content 116 is then used to generate derivedformat versions 110 as indicated by the metadata 114, which may then becommunicated to the service provider system 104 for dissemination. Inthis way, the updated source digital content 116 may be used to generatethe derived format version 110 to include the translated portion 130 inan accurate manner and thus avoid limitations of conventional techniquesthat rely on the derived format version 110. Further discussion oftranslation is described in the following in relation to FIGS. 3-4 andgeneration of derived format version is descried in the following inrelation to FIGS. 5-6, which may be performed automatically and withoutintervention in response to an update to the source digital content.

In general, functionality, features, and concepts described in relationto the examples above and below may be employed in the context of theexample procedures described in this section. Further, functionality,features, and concepts described in relation to different figures andexamples in this document may be interchanged among one another and arenot limited to implementation in the context of a particular figure orprocedure. Moreover, blocks associated with different representativeprocedures and corresponding figures herein may be applied togetherand/or combined in different ways. Thus, individual functionality,features, and concepts described in relation to different exampleenvironments, devices, components, figures, and procedures herein may beused in any suitable combinations and are not limited to the particularcombinations represented by the enumerated examples in this description.

Metadata Link Generation

FIG. 2 depicts a system 200 in an example implementation showinggeneration and management of metadata to link source digital content 116with a derived format version 110 derived from the source digitalcontent 116. The link manager module 122 of the content managementsystem 102 is shown in greater detail as including a metadata generationmodule 202 (e.g., to create or extract metadata) and a link locationmodule 204. The metadata generation module 202 is implemented at leastpartially in hardware of a computing device to generate metadata 114associated with the derived format version 110 and metadata 206associated with source digital content 116.

The metadata generation module 202, for instance, may receive sourcedigital content 116 that includes layers 208 in this example, e.g., textand image layers as found in a PSD formatted file. The metadatageneration module 202 then generates a source content ID 210 (e.g.,created or extracted) as part of the metadata 206 that is usable toidentify and/or locate the source digital content 116, e.g., in a localor remote content repository 118. The metadata 206, for instance, may beextracted if already available or created if not already available. Inone example, metadata 206 is generated “outside”, e.g., when creating aPSD file having source metadata, generation of a JPEG from this fileincludes metadata derived from the source metadata. The metadata 206 isillustrated as stored with the source digital content 116 in thisexample, although other examples are also contemplated, e.g., as part ofa data collection for several different items of source digital contenttogether but that does not actually include the source digital content116.

Likewise, the metadata generation module 202 is also configured togenerate metadata 114 for a derived format version 110 generated fromthe source digital content 116, e.g., extracted or created as describedabove. For example, a format generation system 212 may be included aspart of the digital content manager module 120 to generate the derivedformat version 110 from the source digital content 116, such as togenerate a JPEG, TIFF, or other format from a PSD file. As part ofgenerating the derived format version 110, metadata from the sourcedigital content 116 may be used to derive metadata for the derivedformat version 110.

As part of doing so, the metadata generation module 202 generatesmetadata 114 that includes a source content ID 214 that corresponds tothe source digital content 116, a version ID 216 that identifies aversion of the document (e.g., which may be generated/regenerated whilecopying to a new file path or converted to a new format using “saveas”), and an instance ID 218 that is usable as part of an editinghistory, e.g., generated after selection of “save changes.” A variety ofother examples of metadata 114 are also contemplated, such as a networkaddress via which the source digital content 116 is available, e.g., ofthe content management system 102.

The link location module 204 is then usable to locate a link betweensource digital content 116 and derived format version 110. In oneexample, this is used to locate source digital content 116 to derive anupdated translation of the derived format version 110 as furtherdescribed in relation to FIGS. 3 and 4. In another example, this is usedto automatically generate derived format versions in response to anupdate of the source digital content 116 as further described inrelation to FIGS. 5 and 6.

The metadata generation module 202 may support generation of metadata ina variety of different scenarios, such as to extract metadataautomatically and without user intervention by leveraging definedrelations between source and derived format versions 110. In a firstsuch scenario, the metadata 114 is generated automatically and withoutuser intervention when a derived format version 110 is added to thecontent repository 118 after the source digital content 116. XMPmetadata, for instance, refers to extensible metadata platform metadata,which is an ISO standard for creation, processing, and interchange ofstandardized and custom metadata for digital documents and data sets. Asa part of XMP metadata, a “xmpMM:DerivedFrom” property may be used tostore unique IDs of the source digital content 116 from which thederived format version 110 is derived as a source content ID 214. Thesource content ID 214 “xmpMM:OriginalDocumentID” is used to uniquelyidentify the source digital content 116 as a conceptual entity and isgenerated when the source digital content 116 is created. A version ID216 “xmpM:DocumentID” is used to identify a version of the derivedformat version 110 and is generated when copying the version to a newfile path or conversion to a new format using “save as” by the formatgeneration system 212. The instance ID 218 “xmpMM:InstanceID” is used tosupport an editing history and is generated after changes are saved tothe derived format version 110. For example, the derived format version110 generated as a JPEG from the source digital content 116 may includemetadata 115 having the following values:

-   -   <xmpMM:DerivedFrom stRef:instanceID=    -   “smp.iid: 5D7AEA4C33F3E12A645DCB492B259708”    -   stRef: documentID=    -   “XMP.did:A03F157C0672B72A847BF5CFD70B5F05”    -   stRef:originalDocumentID=    -   “xmp.did:0F7860F72EFCECF302C904E31F366384”/>        Therefore, for a given derived format version 110, corresponding        source digital content 116 may be located by the link location        module 204 through use of the metadata 114. The source digital        content 116 is related automatically and without user        intervention when the source content IDs 210, 214 match, one to        another, e.g.,        “<xmpMM:DerivedFromstRef:instanceID=“xmp.iid:5D7AEA4C33F3E12A6        45DCB493B259708”stRef:documentID=“xmp.did:03F157C0672B72A847BF5CF        D70B5F05”stRef:originalDocumentID=“xmp.did:0F7860F72EFCECF302C904E3        1F366384”/>.” If the IDs do not match, a user verification is        requested. Thus, in this instance the metadata is stored within        the content repository 118.

In an instance in which the metadata is maintained on a service providersystem 104 that is used to upload the source digital content 116 and/orthe derived format version 110, a search may be used by the serviceprovider system 104 to locate the source digital content 116. Thus, inthis example at least part of the functionality of the link managermodule 122 is included on the service provider system 104. In an examplein which the metadata 206 and/or source digital content 116 and derivedformat version 110 are maintained on a third-party service (e.g.,Dropbox®, Box®, Google® Drive), a network address (e.g., URL) of theservice may be included.

In another example in which the source digital content 116 is added tothe content repository 118 after the derived format version 110, themetadata 206, 114 from the source digital content 116 and derived formatversion 110 is extracted. The metadata 206, 114 is then saved as an XMPmetadata property in the content repository 118 to locate the sourcedigital content 116 and/or the derived format version 110. In a furtherexample, manual linking may be performed in which user inputs are usedas a basis by the metadata generation module 202 to generate themetadata 206, 114.

In one instance, the source digital content 116 includes severaldifferent text or image layers, each corresponding to a respectivetranslation, e.g., language type. In such an instance, the layers mayfollow a naming convention, e.g.,“<language-code>-<country-code>_<layer-name>” or“<language-code>_<layer-name>” where:

• <language-code> is ISO0639 standardized two or three letter languagecode; • <country-code> is ISO 3166 standardized two or three lettercountry code; and • <layer-name> is a unique identifier for each layerin a given language, this identifier may be used to generate andsynchronize multiple lingual layers.The following includes examples of use of this convention:

-   -   1. Layer name: background; Description: background (image) layer        that is consistent for each language;    -   2. Layer name: en_title; Description: Title in English language;    -   3. Layer name: fr_title; Description: Title in French language;    -   4. Layer name: en_us_description; Description: Description in        English language for United States; and    -   5. Layer name: en_au_description; Description: Description in        English language for Australia.        During generation of a language specific version of the derived        format version 110 from the source digital content 116, each of        the layers corresponding to textual content of a particular        language are visible, and the rest of the text layers are        hidden. In a scenario involving human translation, an image or        other content may be provided, e.g., an image for which a        globalization equivalent is to be found. Any layer which does        not follow the language layer nomenclature may or may not be        shown. For example, for generating a French derived format        version, the layer with name “fr_title” is shown where the layer        with name “en_title” is hidden. Also, the layer with name        “background” is shown.

The metadata 206, 114, as previously described, may then be used tosupport location of source digital content to aid in translation,further discussion of which is included in the following section andshown in a corresponding figure.

Digital Content Translation

FIG. 3 depicts a system 300 in an example implementation in which atranslation is generated to update source digital content and a derivedformat version. FIG. 3 is depicted using first, second, third, andfourth stages 302, 304, 306, 308. FIG. 4 depicts a procedure 400 in anexample implementation in which a derived format version is updated asincluding a translated version of text, image, and so forth through useof source digital content.

The following discussion describes techniques that may be implementedutilizing the described systems and devices. Aspects of the proceduremay be implemented in hardware, firmware, software, or a combinationthereof. The procedure is shown as a set of blocks that specifyoperations performed by one or more devices and are not necessarilylimited to the orders shown for performing the operations by therespective blocks. In portions of the following discussion, referencewill be made to FIGS. 1-4.

To begin, a request is received at the first stage 302 to translate aderived format version 110 of source digital content 116 (block 402).The request, for instance, may include metadata 114 that is taken fromthe derived format version 110 and communicated to the contentmanagement system 102 via the network 108. The metadata 114 may includean identification of the content management system 102 (e.g., a networkaddress) as well as a source content ID 214.

At the second stage 304, the source digital content 116 is located bythe link manager module 122 of the content management system 102 basedon metadata 114 that is associated with the derived format version 110and is usable to identify the source digital content (block 404). Thelink manager module 122, for instance, may locate a source content ID210 in metadata 206 of the source digital content 116 in the contentrepository 118 that corresponds to the source content ID 214, e.g.,through use of an index.

Once located, text or other portion of the source digital content 116 isextracted from the source digital content (block 406) by the translationmanager module 124. As shown at the third stage 306, for instance, thetranslation manager module 124 of the content management system 102extracts a text layer 310 from the layers 208 of source digital content116. Generation of a translation (i.e., a translated version of thetext) is initiated from the source digital content (block 408). To doso, the text layer 310 (and not other layers 208 of the source digitalcontent 116) is communicated via the network 108 to a translationservice system 106. In this way, the translation service system 106 isprovided with “clean” version of the text or other portion to betranslated, as opposed to conventional techniques that relied oncommunication of the derived format version 110 itself. This also servesto increase network and computational resource efficiency by lowering anamount of data communicated to and processed by the translation servicesystem 106.

The translation service system 106 then employs a digital contenttranslation module 128 to translate the text layer 310 or other portionof the source digital content 116, e.g., an image. In one example, auser interface module 312 is used to output a user interface thatincludes the text layer 310 and receive user inputs to translate text.In another example, an automated translation module 314 is configured togenerate the translation 316 of the text of the text layer 310automatically and without user intervention, e.g., through machinelearning as employed by a neural network of at least one computingdevice. The translation 316, however generated, is then provided back tothe content management system 102 by the translation service system 106via the network 108 in the illustrated example.

At the fourth stage 308, the derived format version is updated asincluding the translated version of the text (block 410). For example,the source digital content is updated using the translation 316, e.g.,the translated version of the text (block 412). The updated derivedformat version is then generated based on the updated source digitalcontent (block 414), e.g., through use of a format generation system212. For instance, a respective layer 208 of the source digital content116 is then updated using the translation, e.g., the text layer 310replaces an existing layer or is appended as an additional layer. Onceupdated, the derived format version 110 is updated (e.g., generatedagain) using the source digital content 116, such as to create a JPEG,TIFF, and so forth. In this way, an accurate and “clean” (i.e., freefrom artifact) derived format version 110 may be generated withincreased network and computational efficiency over conventionaltechniques that relied solely on the derived format version. Generationof the derived format version 110 may also be performed automaticallyand without user intervention in response to an update of the sourcedigital content 116, an example of which is described in the followingsection and shown in corresponding figures.

Automatic Derived Format Generation

FIG. 5 depicts a system 500 in an example implementation in whichderived format versions are automatically generated based on an updateto source digital content. FIG. 6 depicts a procedure 600 in an exampleimplementation in which a several different derived format versions areupdated as including a translated portion through an update to sourcedigital content.

The following discussion describes techniques that may be implementedutilizing the described systems and devices. Aspects of the proceduremay be implemented in hardware, firmware, software, or a combinationthereof. The procedure is shown as a set of blocks that specifyoperations performed by one or more devices and are not necessarilylimited to the orders shown for performing the operations by therespective blocks. In portions of the following discussion, referencewill be made to FIGS. 2, 5 and 6.

As before a request is received to cause translation, which in thisinstance is to cause translation of source digital content (block 602).An input 502, for instance, may be received by an input module 504 ofthe content management system 102. The input 502 may include a requestto translate a derived format version 110 or the source digital content116 itself. For instance, as described in the previous section a requestto translate a derived format version 110 may cause translation ofsource digital content 116. In another instance, the input 502 specifiestranslation of the source digital content directly. Thus, in eitherinstance a source digital content ID 506 may be obtained to locate thesource digital content 116.

A portion of the source digital content is caused to be translated(block 604). The translation manager module 124, for instance, mayextract a portion (e.g., a text layer, image layer, and so forth) fromthe source digital content 116. The portion is then provided to atranslation service system 106 as previously described to obtain thetranslated portion 508. The translated portion 508 is then used toupdate the source digital content 116. In another example, functionalityof the translation service system 106 is employed locally by thetranslation manager module 124 to update the source digital content 116.

A plurality of derived format versions are identified for generationbased on the source digital content. The identification is based onmetadata indicative of a link between the source digital content and theplurality of derived format versions (block 606). In this instance, thelink manager module 122 examines metadata 510 included in the contentrepository that indicates a link between the source digital content 116and corresponding derived format versions 110. As a result, a formatidentification 512 is obtained that identifies which formats have beengenerated and used by service provider system 104 from the contentmanagement system 102. In another instance, each available derivedformat version is generated automatically and without user intervention.

A respective format of the plurality of different format types aregenerated from the source digital content based on the translatedportion (block 608). The format generation system 212, for instance, mayinclude several different format generation modules 514(1)-514(N), eachcorresponding to a different format type, e.g., JPEG, TIFF, and soforth. These several different format generation modules 514(1)-514(N)are used to generate a corresponding derived format version110(1)-110(N) from the updated source digital content 116. In oneexample, this is performed automatically and without user interventionin response to detection of the update to the source digital content116.

Communication is then caused of the plurality of different derivedformat versions, automatically and without user intervention, torespective service provider systems via a network that have obtained therespective format of the source digital content previously from thecontent provider system (block 610). The content management system 102,for instance, may utilize the metadata 510 to locate which serviceprovider systems 104 have obtained respective derived format versions110(1)-110(N) from the source digital content 116. The contentmanagement system 102 may then communicate a notification ofavailability of the updated derived format versions 110(1)-110(N) and/orthe derived format versions 110(1)-110(N), itself. In this way, theupdate to the source digital content 116 triggers the update to thederived format versions 110(1)-110(N). A variety of other examples arealso contemplated.

Example System and Device

FIG. 7 illustrates an example system generally at 700 that includes anexample computing device 702 that is representative of one or morecomputing systems and/or devices that may implement the varioustechniques described herein. This is illustrated through inclusion ofthe digital content manager module 120, link manager module 122, andtranslation manager module 124. The computing device 702 may be, forexample, a server of a service provider, a device associated with aclient (e.g., a client device), an on-chip system, and/or any othersuitable computing device or computing system.

The example computing device 702 as illustrated includes a processingsystem 704, one or more computer-readable media 706, and one or more I/Ointerface 708 that are communicatively coupled, one to another. Althoughnot shown, the computing device 702 may further include a system bus orother data and command transfer system that couples the variouscomponents, one to another. A system bus can include any one orcombination of different bus structures, such as a memory bus or memorycontroller, a peripheral bus, a universal serial bus, and/or a processoror local bus that utilizes any of a variety of bus architectures. Avariety of other examples are also contemplated, such as control anddata lines.

The processing system 704 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 704 is illustrated as including hardware element 710 that may beconfigured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 710 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable storage media 706 is illustrated as includingmemory/storage 712. The memory/storage 712 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage component 712 may include volatile media (such as randomaccess memory (RAM)) and/or nonvolatile media (such as read only memory(ROM), Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage component 712 may include fixed media (e.g., RAM, ROM, afixed hard drive, and so on) as well as removable media (e.g., Flashmemory, a removable hard drive, an optical disc, and so forth). Thecomputer-readable media 706 may be configured in a variety of other waysas further described below.

Input/output interface(s) 708 are representative of functionality toallow a user to enter commands and information to computing device 702,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone, a scanner, touch functionality (e.g., capacitiveor other sensors that are configured to detect physical touch), a camera(e.g., which may employ visible or non-visible wavelengths such asinfrared frequencies to recognize movement as gestures that do notinvolve touch), and so forth. Examples of output devices include adisplay device (e.g., a monitor or projector), speakers, a printer, anetwork card, tactile-response device, and so forth. Thus, the computingdevice 702 may be configured in a variety of ways as further describedbelow to support user interaction.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,” and“component” as used herein generally represent software, firmware,hardware, or a combination thereof. The features of the techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 702. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent and/or non-transitory storage of information incontrast to mere signal transmission, carrier waves, or signals per se.Thus, computer-readable storage media refers to non-signal bearingmedia. The computer-readable storage media includes hardware such asvolatile and non-volatile, removable and non-removable media and/orstorage devices implemented in a method or technology suitable forstorage of information such as computer readable instructions, datastructures, program modules, logic elements/circuits, or other data.Examples of computer-readable storage media may include, but are notlimited to, RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, harddisks, magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other storage device, tangible media, orarticle of manufacture suitable to store the desired information andwhich may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 702, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared, and other wireless media.

As previously described, hardware elements 710 and computer-readablemedia 706 are representative of modules, programmable device logicand/or fixed device logic implemented in a hardware form that may beemployed in some embodiments to implement at least some aspects of thetechniques described herein, such as to perform one or moreinstructions. Hardware may include components of an integrated circuitor on-chip system, an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA), a complex programmable logicdevice (CPLD), and other implementations in silicon or other hardware.In this context, hardware may operate as a processing device thatperforms program tasks defined by instructions and/or logic embodied bythe hardware as well as a hardware utilized to store instructions forexecution, e.g., the computer-readable storage media describedpreviously.

Combinations of the foregoing may also be employed to implement varioustechniques described herein. Accordingly, software, hardware, orexecutable modules may be implemented as one or more instructions and/orlogic embodied on some form of computer-readable storage media and/or byone or more hardware elements 710. The computing device 702 may beconfigured to implement particular instructions and/or functionscorresponding to the software and/or hardware modules. Accordingly,implementation of a module that is executable by the computing device702 as software may be achieved at least partially in hardware, e.g.,through use of computer-readable storage media and/or hardware elements710 of the processing system 704. The instructions and/or functions maybe executable/operable by one or more articles of manufacture (forexample, one or more computing devices 702 and/or processing systems704) to implement techniques, modules, and examples described herein.

The techniques described herein may be supported by variousconfigurations of the computing device 702 and are not limited to thespecific examples of the techniques described herein. This functionalitymay also be implemented all or in part through use of a distributedsystem, such as over a “cloud” 714 via a platform 716 as describedbelow.

The cloud 714 includes and/or is representative of a platform 716 forresources 718. The platform 716 abstracts underlying functionality ofhardware (e.g., servers) and software resources of the cloud 714. Theresources 718 may include applications and/or data that can be utilizedwhile computer processing is executed on servers that are remote fromthe computing device 702. Resources 718 can also include servicesprovided over the Internet and/or through a subscriber network, such asa cellular or Wi-Fi network.

The platform 716 may abstract resources and functions to connect thecomputing device 702 with other computing devices. The platform 716 mayalso serve to abstract scaling of resources to provide a correspondinglevel of scale to encountered demand for the resources 718 that areimplemented via the platform 716. Accordingly, in an interconnecteddevice embodiment, implementation of functionality described herein maybe distributed throughout the system 700. For example, the functionalitymay be implemented in part on the computing device 702 as well as viathe platform 716 that abstracts the functionality of the cloud 714.

Conclusion

Although the invention has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the invention defined in the appended claims is not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as example forms of implementing theclaimed invention.

What is claimed is:
 1. In a digital medium environment to causetranslation of digital content, a method implemented by at least onecomputing device, the method comprising: receiving, by the at least onecomputing device, a request to translate a derived format version ofsource digital content; locating, by the at least one computing device,the source digital content based on metadata associated with the derivedformat version and identifies the source digital content; extracting, bythe at least one computing device, a portion from the source digitalcontent; initiating, by the at least one computing device, generation ofa translated version of the portion from the source digital content; andupdating, by the at least one computing device, the derived formatversion as including the translated version.
 2. The method as describedin claim 1, wherein the metadata links a source content identifier thatidentifies the source digital content to a version identifier thatidentifies the derived format version.
 3. The method as described inclaim 1, wherein the extracting includes identifying a text layer thatincludes the portion as text as part of the source digital content. 4.The method as described in claim 1, wherein the initiating includescommunicating the extracted portion to a translation service system andreceiving the translated version from the translation service system. 5.The method as described in claim 4, wherein the communicating of theextracted portion is performed without communicating the source digitalcontent.
 6. The method as described in claim 1, wherein the updatingincludes updating the source digital content using the translatedversion and generating the updated derived format version based on theupdated source digital content.
 7. The method as described in claim 1,wherein the derived format version is one of a plurality of derivedformat versions generated from the source digital content.
 8. The methodas described in claim 7, wherein each derived format version of theplurality of derived format versions has a different file format, one toanother.
 9. In a digital medium environment to cause automaticgeneration of a plurality of derived format versions responsive to atranslation of source digital content, a system comprising: an inputmodule implemented at least partially in hardware of at least onecomputing device to receive a request to cause translation of sourcedigital content; a translation manager module implemented at leastpartially in hardware of the at least one computing device to cause aportion of the source digital content to be translated; a link managermodule implemented at least partially in hardware of the at least onecomputing device to identify a plurality of derived format versions forgeneration based on the source digital content, the identification basedon metadata indicative of a link between the source digital content andthe plurality of derived format versions; and a plurality of formatgeneration modules implemented at least partially in hardware of the atleast one computing device, each said format generation module isconfigured to generate a respective format of a plurality of differentformat types from the source digital content based on the translatedportion.
 10. The system as described in claim 9, wherein the pluralityof format generation modules are configured to generate the respectiveformat automatically and without user intervention response to receiptof the translated version.
 11. The system as described in claim 9,wherein the translation causation module is configured to communicatethe portion via a network to a translation service system and receivethe translated portion via the network from the translate servicesystem.
 12. The system as described in claim 11, wherein the translationservice system is configured to generate the translated portion throughmachine learning or output of the portion in a user interface andreceipt of user inputs via the user interface that translate theportion.
 13. The system as described in claim 9, wherein the pluralityof different format types include a portable document format, jointphotographic experts group format, or tagged image file format.
 14. Asystem comprising: means for generating metadata including a sourcecontent identifier usable to locate source digital content and at leastone version identifier usable to locate a derived format version of thesource digital content; means for locating the source digital contentbased on the metadata in response to an input to cause translation of atleast a portion of the source digital content; means for causinggeneration of a translated version of the source digital content; meansfor updating the source digital content based on the translated version;and means for generating a plurality of derived format versions from theupdated source digital content.
 15. The system as described in claim 14,further comprising means for extracting text from the source digitalcontent and wherein the translated version of the source digital contentincludes a translation of the extracted text.
 16. The system asdescribed in claim 15, wherein the extracting means is configured toidentify a text layer that includes the portion as text as part of thesource digital content.
 17. The system as described in claim 14, whereinthe translated version is a digital image that is translated from adigital image included in the source digital content.
 18. The system asdescribed in claim 14, wherein the causing means is configured tocommunicate the extracted portion to a translation service system andreceive the translated version from the translation service system. 19.The system as described in claim 18, wherein the communicating of theextracted portion is performed without communicating the source digitalcontent.
 20. The system as described in claim 14, wherein the updatingmeans is configured to update the source digital content using thetranslated version and generate an updated derived format version basedon the updated source digital content.